Conversation
Resolve key fields declared in nested messages (for example metadata.id) across key lookup, indexability checks, order planning, and field-reader path resolution. Add recursive protoc-gen validation to reject invalid/ambiguous nested key declarations and extend tests for nested-key behavior. Signed-off-by: Adphi <philippe.adrien.nousse@gmail.com>
…stry cache Move key field/value resolution and data-prefix derivation behind registry APIs so nested key paths are resolved consistently across db/index paths. Keep legacy inferred-key precedence and add targeted cache invalidation to avoid behavior drift while reducing repeated key lookup logic. Signed-off-by: Adphi <philippe.adrien.nousse@gmail.com>
bcd1dba to
09482d0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.